Skip to content

fix(release): a synchronized copy publishes the version it receives - #224

Merged
Xyzcancer merged 1 commit into
masterfrom
fix/release-copy-keeps-version
Oct 15, 2026
Merged

Xyzcancer merged 1 commit into
masterfrom
fix/release-copy-keeps-version

Conversation

@Xyzcancer

Copy link
Copy Markdown
Contributor

Summary

  • Only the canonical repository numbers releases now (matched by owner id). A synchronized copy no longer runs its own version bump on top of the synced version.properties, which is what put it one minor version ahead on every release.
  • In the copy, merging the synchronization PR tags the version it brings, opens the GitHub release and publishes; an existing tag skips the publish.
  • The copy no longer starts a synchronization of its own.
  • Tag v2.43.0 was placed on the current master once, so this repository's next release is 2.43.1 and both sides carry the same number from then on.

Host impact: none.

@Xyzcancer
Xyzcancer merged commit b8a382c into master Oct 15, 2026
1 check passed
@Xyzcancer
Xyzcancer deleted the fix/release-copy-keeps-version branch October 15, 2026 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant